home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94c.txt
/
000016_icon-group-sender _Mon Dec 19 14:54:50 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-09
|
2KB
Received: by cheltenham.cs.arizona.edu; Mon, 19 Dec 1994 08:32:31 MST
To: icon-group-l@cs.arizona.edu
Date: Mon, 19 Dec 1994 14:54:50 GMT
From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Message-Id: <1994Dec19.145450.20178@kf8nh.wariat.org>
Organization: Brandon's Linux box and AmPR node, Mentor, OH
Sender: icon-group-request@cs.arizona.edu
References: <dkuhlmanD0wuqE.I5w@netcom.com>, <3cv0bd$gdv@highway.leidenuniv.nl>
Subject: Re: Backtracking in Icon
Errors-To: icon-group-errors@cs.arizona.edu
Also sprach ruiter@ruls41.LeidenUniv.nl (Jan-Peter de Ruiter) (<3cv0bd$gdv@highway.leidenuniv.nl>):
+---------------
| G. David Kuhlman (dkuhlman@netcom.com) wrote:
| : But now, in spite of the fact that I have a language
| : with a strong backtracking mechanism, I find that I
| : don't use it much, except of course, for trivial
|
| : constructs like:
|
| : (checkValid(x) | write("error"))
|
| nlines := +argument[1] | 10
| thereby establishing a default value for nlines that can be
| overwritten by a commandline argument. This is a very natural
| formulation that I use very often in my Icon programs.
+------------->8
I think the problem with general use of backtracking is that, while
convenient, it's less efficient than improved algorithms are for any given
task. (Compare recursive vs. nonrecursive algorithms as another example.)
Nevertheless, when it's needed (no readily available non-backtracking
algorithm available in a timely fashion) backtracking is very useful.
++Brandon
--
Brandon S. Allbery KF8NH [44.70.248.67] bsa@kf8nh.wariat.org
Linux development: iBCS2, JNOS, MH ~\U
Controlling application developers is like herding cats. --Oracle DBA Manual